Skip to main content

๐Ÿ“… Schedule Action Configuration

The Schedule action allows your workflow to pause execution until a specific date and time, with support for repeat intervals. This is especially useful for automating timed tasks such as:

  • Sending alerts or reminders
  • Triggering delayed tasks
  • Executing recurring jobs like daily syncs or weekly reports

๐Ÿ”ง Configuration Fieldsโ€‹

๐Ÿท Nameโ€‹

  • Required field.
  • Provide a clear, descriptive name for the scheduled task.

๐Ÿ”› Activeโ€‹

  • Toggle to enable or disable the schedule.
  • Allows pausing the task without removing its configuration.

๐Ÿ•’ Startโ€‹

  • Select the exact date and time when the schedule should begin.
  • Required to initiate the task at the correct moment.

๐Ÿ” Recurrenceโ€‹

Defines how frequently the workflow should run after the initial start time:

  • Run (Once) โ€“ Trigger the workflow a single time.
  • Time โ€“ Delay execution by a specific duration after activation.
  • Daily โ€“ Repeats every day at the specified time.
  • Weekly โ€“ Repeats on selected days of the week.
  • Monthly โ€“ Repeats on selected days of the month.

๐Ÿ”š End Optionsโ€‹

Specify when the recurrence should stop:

  • Never โ€“ Keeps repeating indefinitely.
  • After Occurrences โ€“ Ends after a specified number of repetitions.
  • On Date โ€“ Ends on a specific calendar date and time.

๐Ÿ“ Descriptionโ€‹

  • Optional field to document the purpose of the scheduled task.
  • Useful for teams and future reference.

๐Ÿงช Example JSON Configurationโ€‹

{
"type": "schedule",
"name": "Daily Data Sync",
"active": true,
"start": "2025-05-19T08:00:00Z",
"recurrence": "Daily",
"end": {
"type": "Never"
},
"description": "Runs data synchronization every morning at 8 AM."
}

โœ… Best Use Cases

  • Triggering automated reports on a fixed schedule.
  • Delaying execution for follow-up processes.
  • Automating clean-up or backup operations.
  • Repeating monitoring or health check routines.